Manifest Cargo Details

1. Overview

The Manifest Cargo Details doctype is a child table used within the Manifest document in the VSD Fleet MS module of Frappe ERPNext. It is designed to manage and track detailed cargo information associated with each manifest, such as cargo identification, routing, allocation, and container information.

This doctype enables accurate mapping of cargo movement and allocation decisions across transporters (in-house or sub-contractors), allowing efficient management of shipping logistics and documentation.

2. Key Features

Auto-fetched cargo details from linked Cargo ID
Allocation handling for Trucks, Trailers, and Sub-Contractors
Read-only cargo metadata to maintain data integrity
Support for containerized and non-containerized cargo
Dynamic visibility and access control based on transporter type
Fully integrated with Manifest and related logistics workflow

3. Pre-Requisites

Before using the Manifest Cargo Details doctype, ensure the following:

The Customer and Cargo Registration documents are created and approved.
The Manifest document must be active to embed cargo details.
The user must have read access to the Customer and Cargo Registration doctypes.
Proper cargo routes and transportation options must be pre-defined.
Transporter type logic (In-House vs Sub-Contractor) should be clear and aligned with organizational policy.

4. Step-by-Step Usage

Step 1: Open Manifest

Navigate to Fleet MS > Manifest.
Open an existing Manifest or create a new one.

Step 2: Add Cargo Details

In the Cargo Details child table section, click Add Row.
Select the Cargo ID. Most fields like cargo_type, number_of_package, weight, and bl_number will auto-populate.

Step 3: Specify Allocation

Choose the appropriate Cargo Allocation method: Truck or Trailers.
Based on the Transporter Type, you may enter:
- Specific Cargo Allocated (for in-house truck/trailer)
- Sub-Contractor Cargo Allocation (for sub-contractors)

Step 4: Review Additional Information

Review the read-only fields such as:
- Expected Loading Date
- Expected Offloading Date
- Cargo Route, Seal Number, Container Number, etc.

Step 5: Save the Manifest

Once all cargo details are filled in, save the Manifest to finalize cargo assignment.

5. Script Customizations

Below is the backend logic for this doctype:

class ManifestCargoDetails(Document):
    pass
## 6. Troubleshooting (Common Errors and Resolutions)

| Issue                              | Cause                                                     | Resolution                                                                 |
|------------------------------------|------------------------------------------------------------|----------------------------------------------------------------------------|
| Specific Cargo Allocated not visible | Cargo Allocation is set but Transporter Type is Sub-Contractor | Change transporter type to **In House** to reveal specific cargo fields     |
| Auto-fetch fields not populating  | Incorrect or missing Cargo ID                             | Ensure selected Cargo ID exists and is properly linked                    |
| User cannot edit fields            | Fields are read-only by design                            | Editable fields are controlled by role and DocType config                 |
| Allocation mismatch errors         | Invalid configuration of allocation fields                | Ensure correct use of **Cargo Allocation** vs **Sub-Contractor Cargo Allocation** |

---

## 7. User Roles and Permissions

| Role              | Permissions                                                              |
|-------------------|---------------------------------------------------------------------------|
| **Fleet Manager** | Full access to add, edit, and manage manifest cargo details               |
| **Logistics Officer** | Add and update cargo rows under supervision                        |
| **Data Entry**     | View only or add under specific conditions                               |
| **Sub-Contractor** | Limited access; typically cannot modify manifest entries                 |

> **Note:** Permissions are inherited from the parent **Manifest** document.

---

## 8. Key Notes

- This Doctype is **not meant to be used standalone**. It is a **child table** embedded within **Manifest**.
- Most fields are **read-only** and **auto-fetched** from linked **Cargo** records to ensure data consistency.
- **Dynamic behavior** ensures clarity between **in-house** and **sub-contracted** transportation.

---

## 9. What business process pain point does it help remove

The **Manifest Cargo Details** doctype addresses the following logistics challenges:

- **Manual Entry Errors**: Reduces manual typing by auto-fetching cargo details.
- **Cargo Tracking Complexity**: Enables clear linkage between manifest and individual cargo items.
- **Allocation Ambiguity**: Differentiates between in-house and sub-contracted transport methods using logic-based fields.
- **Data Fragmentation**: Centralizes cargo metadata in one place for dispatchers, managers, and customs officials.

Fleet ms